Add MongoDB log collection target for CVE-2025-14847 #1075
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds MongoDB log collection capabilities to support incident response for CVE-2025-14847 (MongoBleed), a critical memory leak vulnerability in MongoDB's zlib message decompression.
Changes
Targets/Logs/MongoDBLogs.tkape- Collects MongoDB log files from common Windows installation pathsTargets/Compound/ServerTriage.tkape(v1.1) - Now includes MongoDB logsLog Paths Covered
C:\Program Files\MongoDB\Server\*\log\and\logs\C:\data\log\C:\ProgramData\MongoDB\log\C:\MongoDB\log\Why This Matters
MongoBleed exploitation generates distinctive log patterns that are critical for detection:
These logs enable behavioral detection of exploitation attempts against vulnerable MongoDB instances (versions 4.4.0-4.4.29, 5.0.0-5.0.31, 6.0.0-6.0.26, 7.0.0-7.0.27, 8.0.0-8.0.16, 8.2.0-8.2.2).
References
Note
These artifacts were developed on macOS without the ability to validate with KAPE locally. YAML syntax and structure have been validated programmatically and cross-referenced against existing targets in the repository.